The default value for modelType is set to "image" here, which is inconsistent with startDownload (line 558), the restoration logic (line 499), and the decoding logic (line 158), all of which default to "text". To ensure a consistent data contract across the module and with the JavaScript service, this should default to "text".

Fixed — changed default to "text" to be consistent with startDownload, the persistence decoder, and restoreTasksFromSession. JS always passes modelType explicitly for multifile downloads so the default never fired in practice, but the inconsistency has been resolved.

These new fields are being initialized with hardcoded defaults during task restoration. If the app's persisted state in UserDefaults is lost or out of sync, but background URLSessionTasks are still active, the restored DownloadInfo will lose its original modelKey, modelType, combinedTotalBytes, and metadataJson. To ensure robustness and avoid swallowing the state-loss issue with defaults, these fields should be added to the TaskDescription struct so they can be recovered directly from the URLSessionDownloadTask.taskDescription property.

Acknowledged. Adding these fields to TaskDescription is the more robust solution for the edge case where URLSession tasks survive but UserDefaults is wiped. In practice these always travel together on iOS — if UserDefaults is cleared the session tasks are invalidated too. We've accepted this as a known limitation given the added complexity of expanding TaskDescription encoding. The decodeIfPresent fallbacks protect the common upgrade path.

The default value for modelType here is "image", whereas in startDownload (line 558) and restoreTasksFromSession (line 499) it defaults to "text". This inconsistency can lead to unexpected behavior. Consider using a consistent default or ensuring the type is explicitly passed from the JavaScript side.

Fixed — changed default to "text" to match startDownload and the rest of the module.

The nextDownloadId is being accessed and incremented outside of the synchronized queue. Since this module uses a concurrent queue for state management and can be called from multiple threads via the React Native bridge, this creates a race condition that could lead to duplicate downloadId values.

Fixed — nextDownloadId read and increment are now wrapped in queue.sync(flags: .barrier) matching the rest of the module's state management pattern.

The iOS implementation returns the timestamp as startedAt, but the TypeScript service (line 90) and the Android implementation use createdAt. To ensure cross-platform compatibility and correct hydration in the JS layer, it is recommended to include the createdAt key in the response.

          "startedAt": NSNumber(value: info.startedAt),
          "createdAt": NSNumber(value: info.startedAt),
          "modelType": info.modelType,
          "combinedTotalBytes": NSNumber(value: info.combinedTotalBytes)

Fixed — getActiveDownloads now includes a createdAt key aliased from startedAt so the JS mapper receives the correct field name on both platforms.

The default modelType here is set to "image", which is inconsistent with startDownload (line 558), the persistence decoder (line 158), and the session restoration logic (line 499), all of which default to "text". This inconsistency can lead to models being incorrectly categorized depending on the download method used or after an app restart.

Fixed — changed default to "text" for consistency across the module.